Updating software based on similarities between endpoints

ABSTRACT

An apparatus for updating software or changing configuration of software installed in a plurality of terminals, including: a recognition unit for recognizing that the software installed in a first terminal has been successfully updated or the configuration of the software installed in the first terminal has been successfully changed; a selection unit for selecting, in response to the recognition that the software installed in the first terminal has been successfully updated or the configuration of the software installed in the first terminal has been successfully changed, a second terminal in a case where a degree of similarity between a configuration of the first terminal and a configuration of the second terminal is equal to or higher than a predetermined reference value; and an instruction unit for giving an instruction to update the software or to change the configuration of the software installed in the second terminal.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority to Japanese PatentApplication No. 2014-158877, filed Aug. 4, 2014, the entire contents ofwhich are incorporated herein by reference.

TECHNICAL FIELD

The present invention relates to an apparatus and a method for updatingsoftware or for changing configuration of software. In particular, thepresent invention relates to an apparatus and a method for updatingsoftware or for changing configuration of software installed in aplurality of terminals.

BACKGROUND ART

Along with development of IT technology, a wide variety of devices areused in organizations such as companies. Under the circumstance, burdensof management of devices (endpoints) on the organizations such ascompanies are rapidly increasing, and hence an endpoint managementproduct is attracting attention (see, for example, Non-patent Literature1).

In general, the endpoint management product provides a function ofperforming a configuration change on an endpoint. Here, theconfiguration change on the endpoint refers to a configuration change ofa system or an application in the endpoint, and includes patching andapplication introduction. The endpoint management product also providesa function of remotely applying a configuration change to a plurality ofendpoints at a time.

Further, in the endpoint management product, an endpoint as anapplication target of a configuration change can be generally designatedusing a conditional expression and the like. Specifically, the endpointas the application target can be selected by designating the version ofan operating system (OS), an application and patching conditionsconcerning the configuration change, and the configuration of the system(such as the value of a particular registry).

In the case of applying a configuration change to endpoints using theendpoint management product as described above, the following method isgenerally adopted. That is, a system department or the like applies inadvance the configuration change to a test environment of an endpointhaving a general configuration. After sufficiently testing that atrouble does not occur, the system section or the like applies theconfiguration change to endpoints of general users.

In addition to the above, a technique of setting up software in commonfor a plurality of apparatuses is known (see, for example, PatentLiterature 1).

Patent Literature 1 discloses a technique in which an analysis apparatusdetermines common software to be set up for its own apparatus, reads outconfiguration information corresponding to the common software from astorage medium, compares configuration information on its own apparatuswith the read-out information, determines an apparatus having the sameconfiguration or an apparatus having a similar configuration from amongapparatuses for which the common software has been set up, reads outset-up result information on the apparatus having the same configurationor the apparatus having a similar configuration from the storage medium,and outputs the read-out information as set-up success/failureinformation on the common software.

Moreover, a technique of making a processing program common to differentdatabase groups is also known (see, for example, Patent Literature 2).

Patent Literature 2 discloses a database system in which: an operatingsystem reads setting information and determines which database is to beconnected; when a compiler complies a database processing program(source format) in which a database to be processed is not specified,the compiler identifies a database to be processed in each step, on thebasis of description of environment information recorded in a currentlyconnected database; and the database processing program (object format)thus compiled is executed on a database group.

Further, a technique of constructing a calculator environment equivalentto various user PCs is also known (see, for example, Patent Literature3).

Patent Literature 3 discloses an execution environment constructionapparatus including: an environment configuration data creation unit forcalculating the degree of demand of environment configuration data closeto a user environment information DB demanded by a user, andconstructing an execution environment on an execution terminal on thebasis of the calculated degree of demand; and an environmentconfiguration data selection unit for selecting environmentconfiguration data having a degree of environment similarity close tothe user environment information, from the execution terminal on whichthe execution environment is constructed. The execution environmentconstruction apparatus constructs an execution environment configured bya software resource including at least one operating system, on anexecution terminal.

CITATION LIST Patent Literatures

[Patent Literature 1] JP2009-277130A

[Patent Literature 2] JP2006-244383A

[Patent Literature 3] JP2012-221170A

Non Patent Literature

IBM Endpoint Manager V9.1, available from International BusinessMachines Corporation.

As described above, in the case of applying a configuration change toendpoints using the endpoint management product as described inNon-patent Literature 1, conventionally, a test environment of anendpoint is prepared, and the configuration change is applied to thetest environment.

Unfortunately, particularly in organizations such as companies includinga large number of users, it is not realistic to prepare a testenvironment that covers the configurations of endpoints of all theusers. Hence, there is a problem that, if a configuration change isapplied to an environment having a configuration that is not consideredat the time of testing, a trouble in operation may occur.

Moreover, this problem does not limitatively occur in the case ofapplying the configuration change to the test environment, and can alsooccur in the case of updating software installed in a general terminal.That is, there is a problem that, even if software installed in oneterminal has been successfully updated, software installed in anotherterminal is not necessarily successfully updated.

Note that the techniques of Patent Literatures 1 to 3 do not providemeans for solving such problems.

SUMMARY OF INVENTION

The present invention has an object to enhance the possibility that, ifsoftware installed in one terminal has been successfully updated, thesoftware installed in another terminal is also successfully updated.

Solution to Problems

In order to achieve the above-mentioned object, the present inventionprovides an apparatus for updating software or changing configuration ofsoftware installed in a plurality of terminals, including: a recognitionunit for recognizing that the software installed in a first terminal ofthe plurality of terminals has been successfully updated or theconfiguration of the software installed in a first terminal of theplurality of terminals has been successfully changed; a selection unitfor selecting, in response to the recognition that the softwareinstalled in the first terminal has been successfully updated or theconfiguration of the software installed in the first terminal has beensuccessfully changed, a second terminal of the plurality of terminals ina case where a degree of similarity between a configuration of the firstterminal and a configuration of the second terminal is equal to orhigher than a predetermined reference value; and an instruction unit forgiving an instruction to update the software or to change theconfiguration of the software installed in the second terminal.

The present invention also provides a method for updating software orfor changing configuration of software installed in a plurality ofterminals, including the steps of: giving an instruction to update thesoftware or to change the configuration of the software installed in afirst terminal of the plurality of terminals; recognizing that thesoftware installed in the first terminal has been successfully updatedor the configuration of the software installed in the first terminal hasbeen successfully changed; selecting, in response to the recognitionthat the software installed in the first terminal has been successfullyupdated or the configuration of the software installed in the firstterminal has been successfully changed, a second terminal of theplurality of terminals in a case where a degree of similarity between aconfiguration of the first terminal and a configuration of the secondterminal is equal to or higher than a predetermined reference value; andgiving an instruction to update the software or to change theconfiguration of the software installed in the second terminal.

The present invention also provides a program for causing a computer tofunction as an apparatus for updating software or changing configurationof software installed in a plurality of terminals, the program causingthe computer to function as: a recognition unit for recognizing that thesoftware installed in a first terminal of the plurality of terminals hasbeen successfully updated or the configuration of the software installedin a first terminal of the plurality of terminals has been successfullychanged; a selection unit for selecting, in response to the recognitionthat the software installed in the first terminal has been successfullyupdated or the configuration of the software installed in a firstterminal of the plurality of terminals has been successfully changed, asecond terminal of the plurality of terminals in a case where a degreeof similarity between a configuration of the first terminal and aconfiguration of the second terminal is equal to or higher than apredetermined reference value; and an instruction unit for giving aninstruction to update the software or to change the configuration of thesoftware installed in the second terminal.

Advantageous Effect of Invention

The present invention can enhance the possibility that, if softwareinstalled in one terminal has been successfully updated, the softwareinstalled in another terminal is also successfully updated.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating a function configuration example of anendpoint management system according to an embodiment of the presentinvention;

FIG. 2A, FIG. 2B, and FIG. 2C are diagrams each illustrating a specificexample of information stored in a configuration information DB;

FIG. 3 is a diagram illustrating a specific example of informationstored in a working status DB;

FIG. 4 is a diagram illustrating a specific example of informationstored in a change history DB;

FIG. 5 is a flowchart illustrating an operation example of an endpointmanagement server according to the embodiment of the present invention;

FIG. 6 is a flowchart illustrating an operation example of the endpointmanagement server according to the embodiment of the present invention;

FIG. 7 is a diagram for specifically describing a first method forcalculating the degree of similarity by a degree-of-similaritycalculation unit according to the embodiment of the present invention;

FIG. 8A and FIG. 8B are diagrams for specifically describing a secondmethod for calculating the degree of similarity by thedegree-of-similarity calculation unit according to the embodiment of thepresent invention;

FIG. 9A and FIG. 9B are diagrams for specifically describing a methodfor calculating an interorganization distance by an application targetdetermination unit according to the embodiment of the present invention;and

FIG. 10 is a diagram illustrating a hardware configuration example ofthe endpoint management server according to the embodiment of thepresent invention.

DESCRIPTION OF EMBODIMENT

Hereinafter, an embodiment of the present invention is described indetail with reference to the attached drawings.

In order to achieve the above-mentioned object, the present inventionprovides an apparatus for updating software or changing configuration ofsoftware installed in a plurality of terminals, including: a recognitionunit for recognizing that the software installed in a first terminal ofthe plurality of terminals has been successfully updated or theconfiguration of the software installed in a first terminal of theplurality of terminals has been successfully changed; a selection unitfor selecting, in response to the recognition that the softwareinstalled in the first terminal has been successfully updated or theconfiguration of the software installed in the first terminal has beensuccessfully changed, a second terminal of the plurality of terminals ina case where a degree of similarity between a configuration of the firstterminal and a configuration of the second terminal is equal to orhigher than a predetermined reference value; and an instruction unit forgiving an instruction to update the software or to change theconfiguration of the software installed in the second terminal.

Here, the selection unit may select the second terminal in a case wherea degree of priority of a user of the second terminal is equal to orhigher than a predetermined reference value.

Moreover, the selection unit further may select, in response to therecognition that the software installed in the first terminal has beensuccessfully updated or the configuration of the software installed inthe first terminal has been successfully changed, a third terminal ofthe plurality of terminals in a case where a degree of similaritybetween the configuration of the first terminal and a configuration ofthe third terminal is equal to or higher than a predetermined referencevalue. The instruction unit may further give an instruction to updatethe software or to change the configuration of the software installed inthe third terminal. In this case, the selection unit may select thesecond terminal and the third terminal in a case where a degree ofassociation between a user of the second terminal and a user of thethird terminal satisfies a predetermined condition. Alternatively, theselection unit may select the second terminal and the third terminal ina case where a degree of association between an installation place ofthe second terminal and an installation place of the third terminalsatisfies a predetermined condition.

Moreover, the recognition unit may recognize that the software installedin a third terminal of the plurality of terminals has been successfullyupdated or the configuration of the software installed in a thirdterminal of the plurality of terminals has been successfully changed.The selection unit may select, in response to the recognition that thesoftware installed in the third terminal has been successfully updatedor the configuration of the software installed in the third terminal ofthe plurality of terminals has been successfully changed, a fourthterminal of the plurality of terminals in a case where at least any oneof: a degree of similarity between the configuration of the firstterminal and a configuration of the fourth terminal; and a degree ofsimilarity between a configuration of the third terminal and theconfiguration of the fourth terminal is equal to or higher than apredetermined reference value. The instruction unit may give aninstruction to update the software or to change the configuration of thesoftware installed in the fourth terminal.

Further, this apparatus may further include a generation unit forgenerating information indicating a difference between a configurationof a third terminal of the plurality of terminals and a configuration ofa fourth terminal of the plurality of terminals, in a case where it isnot recognized that the software installed in the fourth terminal hasbeen successfully updated or the configuration of the software installedin the fourth terminal has been successfully changed after it isrecognized that the software installed in the third terminal has beensuccessfully updated or the configuration of the software installed inthe third terminal of the plurality of terminals has been successfullychanged.

The present invention also provides an apparatus for updating softwareor for changing configuration of software installed in a plurality ofterminals, including: a recognition unit for recognizing that thesoftware installed in a configuration change verification terminal ofthe plurality of terminals has been successfully updated or theconfiguration of the software installed in a configuration changeverification terminal of the plurality of terminals has beensuccessfully changed, the configuration change verification terminalbeing for verifying the update of the software; a selection unit forselecting, in response to the recognition that the software installed inthe configuration change verification terminal has been successfullyupdated or the configuration of the software installed in theconfiguration change verification terminal has been successfullychanged, update execution terminals of the plurality of terminals indescending order of a degree of similarity between a configuration ofthe configuration change verification terminal and a configuration ofeach of the update execution terminals, the update execution terminalsbeing for executing the update of the software; and an instruction unitfor giving an instruction to update the software or to change theconfiguration of the software installed in each of the update executionterminals, in the order in which the update execution terminals areselected.

The present invention also provides a method for updating software orfor changing configuration of software installed in a plurality ofterminals, including the steps of: giving an instruction to update thesoftware or to change the configuration of the software installed in afirst terminal of the plurality of terminals; recognizing that thesoftware installed in the first terminal has been successfully updatedor the configuration of the software installed in the first terminal hasbeen successfully changed; selecting, in response to the recognitionthat the software installed in the first terminal has been successfullyupdated or the configuration of the software installed in the firstterminal has been successfully changed, a second terminal of theplurality of terminals in a case where a degree of similarity between aconfiguration of the first terminal and a configuration of the secondterminal is equal to or higher than a predetermined reference value; andgiving an instruction to update the software or to change theconfiguration of the software installed in the second terminal.

The present invention also provides a program for causing a computer tofunction as an apparatus for updating software or changing configurationof software installed in a plurality of terminals, the program causingthe computer to function as: a recognition unit for recognizing that thesoftware installed in a first terminal of the plurality of terminals hasbeen successfully updated or the configuration of the software installedin a first terminal of the plurality of terminals has been successfullychanged; a selection unit for selecting, in response to the recognitionthat the software installed in the first terminal has been successfullyupdated or the configuration of the software installed in a firstterminal of the plurality of terminals has been successfully changed, asecond terminal of the plurality of terminals in a case where a degreeof similarity between a configuration of the first terminal and aconfiguration of the second terminal is equal to or higher than apredetermined reference value; and an instruction unit for giving aninstruction to update the software or to change the configuration of thesoftware installed in the second terminal.

Outline of Present Embodiment

In the present embodiment, the degree of similarity between an endpointused for advance testing of a configuration change and each of the otherendpoints is calculated using pieces of configuration information on aplurality of endpoints collected by an endpoint management product.Here, the configuration information includes, for example, the type andversion of an OS, patching conditions, introduced applications, ahardware configuration, and configuration values (such as registries) ofthe system and the applications. Then, the endpoints are selected indescending order of the degree of similarity, and the configurationchange is sequentially applied to the selected endpoints.

Moreover, in the present embodiment, in the case where a configurationchange has been successfully applied to a given endpoint or a group ofendpoints each having a configuration similar to that of the givenendpoint, the configuration change is applied to the subsequent endpointor group. Here, the expression that “a configuration change issuccessfully applied” may refer to that the configuration change can beapplied, and, in the present embodiment, this expression refers to thatno occurrence of a trouble can be confirmed within a predeterminedoperation evaluation period after the configuration change is applied.

At this time, in order to enhance the expansion speed of the range ofendpoints as application targets, a part or the entirety of endpoints towhich the configuration change has been successfully applied may besequentially added as new reference endpoints for calculating the degreeof similarity. Then, endpoints as new application targets may bedetermined on the basis of the degrees of similarity between thereference endpoints and each of the other endpoints.

Moreover, an endpoint as an application target may be determined on thebasis of not only the degree of similarity between the configurations ofendpoints but also multidimensional indexes. The multidimensionalindexes include the degree of association between users of endpoints,the degree of association between installation places of endpoints, andthe degree of priority of a user of an endpoint.

Among these indexes, the degree of association between users refers to,for example, the distance between organizations to which the usersrespectively belong (interorganization distance). The interorganizationdistance is obtained on the basis of organization information.Specifically, it is conceivable not to simultaneously apply aconfiguration change to a plurality of endpoints respectively used by aplurality of users who belong to close organizations. This can minimizean influence on business in case of trouble. It is also conceivable topreferentially apply a configuration change to a plurality of endpointsrespectively used by a plurality of users who are connected to oneanother on a social networking service (SNS).

Moreover, the degree of association between installation places refersto, for example, the distance between the installation places.Specifically, in order to suppress a burden on communication lines, itis conceivable to limit the number of endpoints to which a configurationchange is simultaneously applied, in the same business office.

Further, the degree of priority of a user refers to, for example, an ITskill level. Specifically, it is conceivable to preferentially apply aconfiguration change to an endpoint used by a user having a high ITskill level and then apply the configuration change to endpointsrespectively used by users around the user having the high IT skilllevel. In this case, the user having the high IT skill level may beidentified on the basis of working records of a registry editor, asystem tool, and the like.

Moreover, the multidimensional indexes may include the use time and usefrequency of an endpoint and the use time and use frequency of aparticular application running on the endpoint.

Further, in the present embodiment, in the case where a trouble occurswhen a configuration change is applied to a given endpoint, a differencebetween: the configuration of an endpoint to which the configurationchange has been successfully applied immediately before; and theconfiguration of the given endpoint in which the trouble occurs may bepresented. In this way, determination of a problem concerning a failurein applying the configuration change or setting of conditions inapplying the configuration change may be supported.

Function Configuration of Endpoint Management System according toPresent Embodiment

FIG. 1 is a diagram illustrating a function configuration example of anendpoint management system according to the present embodiment. Asillustrated in FIG. 1, the endpoint management system includesmanagement target endpoints 10 a to 10 c, a test environment endpoint20, an endpoint management server 30, an endpoint management console 40,an asset information server 50, and an organization information server60. Then, the endpoint management server 30 is connected to themanagement target endpoints 10 a to 10 c, the test environment endpoint20, the endpoint management console 40, the asset information server 50,and the organization information server 60, through communication lines(not illustrated) such as a local area network (LAN). Note that,although distinctively illustrated in FIG. 1, the management targetendpoints 10 a to 10 c are referred to as the management targetendpoint(s) 10 in the case where the management target endpoints 10 a to10 c do not need to be distinguished from one another. Moreover,although only three management target endpoints 10 are illustrated inFIG. 1, in general, more than three management target endpoints 10 areconnected.

Each management target endpoint 10 is an endpoint as a target to bemanaged in the endpoint management system. A management agent 11 isintroduced in the management target endpoint 10, and the managementagent 11 includes an information acquisition unit 12 and a configurationchange execution unit 13. The information acquisition unit 12 acquires:configuration information indicating the configurations of hardware, anOS, applications, patches, and the like; and the working statuses of thehardware, the OS, the application, and the like. The configurationchange execution unit 13 receives an instruction from the endpointmanagement server 30 to execute a process of applying a configurationchange. Here, a desktop personal computer (PC), a notebook PC, a tabletPC, a personal digital assistant (PDA), a smartphone, and the like maybe used as the management target endpoint 10.

The test environment endpoint 20 is an endpoint having a testenvironment for testing whether or not the configuration change issuccessfully applied to the management target endpoint 10 before theconfiguration change is applied thereto. A management agent 21 isintroduced in the test environment endpoint 20. The configuration of themanagement agent 21 is similar to that of the management agent 11introduced in the management target endpoint 10, and hence detaileddescription thereof is omitted. Here, a desktop PC, a notebook PC, atablet PC, a PDA, a smartphone, and the like may be used as the testenvironment endpoint 20.

The endpoint management server 30 is a server computer in which theendpoint management product is installed, the server computer managingendpoints while controlling the management agent 11 introduced in themanagement target endpoint 10 and the management agent 21 introduced inthe test environment endpoint 20. More detailed configuration thereof isdescribed later. Here, a desktop PC and the like may be used as theendpoint management server 30.

The endpoint management console 40 is an input/output apparatus that isused by a system administrator to: instruct the endpoint managementserver 30 to apply the configuration change; and receive presentation ofinformation from the endpoint management server 30.

The asset information server 50 is a server computer for holding assetinformation on assets managed by an organization such as a companyincluding the endpoint management system. The asset information server50 provides the asset information to the endpoint management server 30,in response to a request from the endpoint management server 30.

The organization information server 60 is a server computer for holdingorganization information on an internal organization such as adepartment in the organization such as the company including theendpoint management system. The organization information server 60provides the organization information to the endpoint management server30, in response to a request from the endpoint management server 30.

Here, a function configuration of the endpoint management server 30 isdescribed in detail. As illustrated in FIG. 1, the endpoint managementserver 30 includes an information collection unit 31, a configurationinformation DB 32, a working status DB 33, a change history DB 34, adegree-of-similarity calculation unit 35, an application targetdetermination unit 36, and a configuration change instruction unit 37.

The information collection unit 31 collects the configurationinformation and the working status of the management target endpoint 10from the information acquisition unit 12 of the management agent 11, andcollects the configuration information and the working status of thetest environment endpoint 20 from the information acquisition unit 22 ofthe management agent 21. Moreover, the information collection unit 31collects a result of applying the configuration change to the managementtarget endpoint 10, from the configuration change execution unit 13 ofthe management agent 11, and collects a result of applying theconfiguration change to the test environment endpoint 20, from theconfiguration change execution unit 23 of the management agent 21. Then,the information collection unit 31 determines whether or not theconfiguration change has been successfully applied. In the presentembodiment, the information collection unit 31 is provided as an exampleof a recognition unit for recognizing that software has beensuccessfully updated.

The configuration information DB 32 is a database for storingconfiguration information collected by the information collection unit31. Specific contents of the configuration information DB 32 aredescribed later.

The working status DB 33 is a database for storing working statusescollected by the information collection unit 31. Specific contents ofthe working status DB 33 are described later.

The change history DB 34 is a database for storing change historiescollected by the information collection unit 31. Specific contents ofthe change history DB 34 are described later.

The degree-of-similarity calculation unit 35 calculates the degree ofsimilarity between a reference endpoint and each management targetendpoint 10, on the basis of the pieces of data stored in theconfiguration information DB 32, the working status DB 33, and thechange history DB 34. Moreover, the degree-of-similarity calculationunit 35 initially sets the test environment endpoint 20 to the referenceendpoint, and then sets any of the management target endpoints 10 towhich the configuration change has been successfully applied, to thereference endpoint as needed. Moreover, in the case where application ofthe configuration change to a given management target endpoint 10 hasbeen failed, the degree-of-similarity calculation unit 35 extracts adifference between the configuration of the given management targetendpoint 10 and the configuration of the management target endpoint 10to which the configuration change has been successfully appliedimmediately before, and outputs the difference to the endpointmanagement console 40. In the present embodiment, thedegree-of-similarity calculation unit 35 is provided as an example of ageneration unit for generating information indicating the difference.

The application target determination unit 36 determines the managementtarget endpoint 10 to which the configuration change is to be applied,on the basis of the degree of similarity calculated by thedegree-of-similarity calculation unit 35. Alternatively, the applicationtarget determination unit 36 may determine the management targetendpoint 10 to which the configuration change is to be applied, on thebasis of not only the degree of similarity but also information such asthe degree of association between users of endpoints, the degree ofassociation between installation places of endpoints, and the degree ofpriority of a user of an endpoint. The number of the management targetendpoints 10 that are determined at a time as application targets of theconfiguration change may be one. In the present embodiment, a group of aplurality of the management target endpoints 10 is determined as anapplication target of the configuration change. In the presentembodiment, the application target determination unit 36 is provided asan example of a selection unit for selecting a terminal.

Upon reception of an instruction given by the system administrator fromthe endpoint management console 40, the configuration change instructionunit 37 transmits an instruction to apply the configuration change tothe test environment endpoint 20, to the configuration change executionunit 23 of the management agent 21. Moreover, when the management targetendpoint 10 to which the configuration change is to be applied isdetermined by the application target determination unit 36, theconfiguration change instruction unit 37 transmits an instruction toapply the configuration change to the determined management targetendpoint 10, to the configuration change execution unit 13 of themanagement agent 11. In the present embodiment, the configuration changeinstruction unit 37 is provided as an example of an instruction unit forgiving an instruction to update software or to change configuration ofsoftware.

Here, the contents of the information stored in the configurationinformation DB 32 are described. FIGS. 2A to 2C are diagrams eachillustrating a specific example of the information stored in theconfiguration information DB 32.

FIG. 2A illustrates a basic information table in which basic informationthat is fundamental information on each endpoint is stored. Asillustrated in FIG. 2A, the basic information table includes an endpointID, last update date and time, a model number, a memory capacity, a HDDcapacity, a HDD space, and OS information. Among these pieces ofinformation, the endpoint ID is identification information foridentifying an endpoint, and the OS information is informationindicating the type and version of an OS mounted on the endpoint. Thatis, the basic information table serves to manage which version of whichOS is mounted on the endpoint identified by each endpoint ID. Forexample, the first row shows that Japanese-language version of Windows®7, Service Pack 1 is mounted on an endpoint “PC001”.

FIG. 2B illustrates an application information table in whichinformation on applications installed in each endpoint is stored. Asillustrated in FIG. 2B, the application information table includes anendpoint ID, an application name, a version, and a category. That is,the application information table serves to manage which version ofwhich application is installed as an application in each category in theendpoint identified by each endpoint ID.

FIG. 2C illustrates a device information table in which information on adevice mounted on each endpoint is stored. As illustrated in FIG. 2C,the device information table includes an endpoint ID, a device name, adriver version, and a category. That is, the device information tableserves to manage which driver version of which device is installed as adevice in each category in the endpoint identified by each endpoint ID.

Moreover, the contents of the information stored in the working statusDB 33 are described. FIG. 3 is a diagram illustrating a specific exampleof the information stored in the working status DB 33. As illustrated inFIG. 3, the working status DB 33 includes an endpoint ID, eventoccurrence date and time, a target, and a state. That is, the workingstatus DB 33 serves to manage in which target an event occurs and whatthe current state of the event is, in the endpoint identified by eachendpoint ID.

Further, the contents of the information stored in the change history DB34 are described. FIG. 4 is a diagram illustrating a specific example ofthe information stored in the change history DB 34. As illustrated inFIG. 4, the change history DB 34 includes an endpoint ID, last updatedate and time, a configuration change ID, and a state. Among thesepieces of information, the configuration change ID is identificationinformation for identifying a configuration change. An external table isreferred to with the configuration change ID being used as a key,whereby detailed information on the configuration change can beacquired. Here, the detailed information on the configuration changeincludes the degree of urgency of the configuration change andconditions for applying the configuration change. Moreover, the state isa state of an endpoint after the configuration change is applied, andany of “Success”, “Fail”, and “In-Progress” is set to the state. Amongthese states, “Success” refers to a state in which no problem occurseven after the elapse of a predetermined evaluation period from theapplication of the configuration change, that is, a state in which theconfiguration change has been successfully applied. “Fail” refers to astate in which the configuration change has not been successfullyapplied or a state in which a problem occurs within the predeterminedevaluation period from the application of the configuration change, thatis, a state in which the application of the configuration change hasbeen failed. “In-Progress” is a state in which whether or not a problemoccurs is being evaluated after the configuration change is applied.That is, the change history DB 34 serves to manage a result of applyingthe configuration change to the endpoint identified by each endpoint ID.

Operation of Endpoint Management Server according to Present Embodiment

Next, an operation of the endpoint management server 30 according to thepresent embodiment is described. Prior to the operation, in the endpointmanagement server 30, first, the information collection unit 31collects: the configuration information and the working status of themanagement target endpoint 10 acquired by the information acquisitionunit 12 of the management agent 11; and the configuration informationand the working status of the test environment endpoint 20 acquired bythe information acquisition unit 22 of the management agent 21, and theinformation collection unit 31 stores the pieces of configurationinformation in the configuration information DB 32 and stores theworking statuses in the working status DB 33. The information collectionunit 31 also collects: a result of applying a configuration change tothe management target endpoint 10 by the configuration change executionunit 13 of the management agent 11; and a result of applying theconfiguration change to the test environment endpoint 20 by theconfiguration change execution unit 23 of the management agent 21, andthe information collection unit 31 stores the results as changehistories of the configurations of the endpoints in the change historyDB 34.

It is assumed that, in this state, the system administrator instructsthe endpoint management server 30 to apply the configuration change tothe test environment endpoint 20, through the endpoint managementconsole 40. This starts the operation of the endpoint management server30. FIG. 5 and FIG. 6 are flowcharts each illustrating an operationexample to be subsequently performed by the endpoint management server30.

In the endpoint management server 30, first, as illustrated in FIG. 5,the configuration change instruction unit 37 transmits an instruction toapply the configuration change, to the configuration change executionunit 23 of the management agent 21 (Step 301). In response to this, theconfiguration change execution unit 23 of the management agent 21applies the configuration change to the test environment endpoint 20. Atthis time, the system administrator designates which endpoint is to bedefined as the test environment endpoint 20, using the correspondingendpoint ID, and designates which configuration change is to be applied,using the corresponding configuration change ID. Consequently, the usedendpoint ID and the used configuration change ID are delivered from theconfiguration change instruction unit 37 to the information collectionunit 31.

After that, the information collection unit 31 collects a result ofapplying the configuration change to the test environment endpoint 20,from the configuration change execution unit 23 of the management agent21, and stores the result in the change history DB 34 (Step 302).Specifically, the information collection unit 31 stores the endpoint ID,the configuration change ID, and a state after the configuration changeis applied, in the change history DB 34. Alternatively, at this time,the information collection unit 31 may report the obtained result to thesystem administrator through the endpoint management console 40.

Upon the collection of the result of applying the configuration changein this way, the information collection unit 31 determines whether ornot the configuration change has been successfully applied to the testenvironment endpoint 20 (Step 303). As a result, if it is determinedthat the configuration change has not been successfully applied to thetest environment endpoint 20, the endpoint management server 30 ends theprocessing. On the other hand, if it is determined that theconfiguration change has been successfully applied to the testenvironment endpoint 20, the endpoint management server 30 proceeds to aprocess of applying the same configuration change to every managementtarget endpoint 10. At this time, the endpoint ID and the configurationchange ID that have been delivered from the configuration changeinstruction unit 37 to the information collection unit 31 are furtherdelivered to the degree-of-similarity calculation unit 35.

Consequently, the degree-of-similarity calculation unit 35 sets thereceived endpoint ID, that is, the endpoint ID of the test environmentendpoint 20 to the endpoint ID of a reference endpoint that serves as areference for calculating the degree of similarity (Step 304).Alternatively, the system administrator may check the result of applyingthe configuration change that is reported through the endpointmanagement console 40, and may give an instruction to apply the sameconfiguration change to every management target endpoint 10, through theendpoint management console 40. At this time, the system administratordesignates the endpoint ID of the test environment endpoint 20 as theendpoint ID of the reference endpoint that serves as the reference forcalculating the degree of similarity, and designates the configurationchange ID of the configuration change that has been applied to the testenvironment endpoint 20, as the configuration change ID of theconfiguration change to be applied to every management target endpoint10.

As a result, in the endpoint management server 30, as illustrated inFIG. 6, the degree-of-similarity calculation unit 35 calculates thedegree of similarity between the reference endpoint and each managementtarget endpoint 10, on the basis of the pieces of data stored in theconfiguration information DB 32, the working status DB 33, and thechange history DB 34 (Step 321). Note that, in the first operation, thereference endpoint is only the test environment endpoint 20. Moreover,at this time, the degree-of-similarity calculation unit 35 may store thecalculated degree of similarity in a degree-of-similarity DB (notillustrated). The details of a method for calculating the degree ofsimilarity are described later.

Subsequently, the application target determination unit 36 determinesthe management target endpoint 10 to which the configuration change isto be applied, on the basis of the degree of similarity calculated bythe degree-of-similarity calculation unit 35 (Step 322). At this time,basically, the application target determination unit 36 determines, asan application target, a group including the management target endpoints10 for which the highest degree of similarity is calculated. Forexample, the application target determination unit 36 may select apredetermined number of the management target endpoints 10 in descendingorder of the degree of similarity, and may determine a group includingthe selected management target endpoints 10 as the application target.Alternatively, the application target determination unit 36 may selectthe management target endpoints 10 each having a degree of similarityequal to or higher than a predetermined value, and may determine a groupincluding the selected management target endpoints 10 as the applicationtarget.

Alternatively, the application target determination unit 36 maydetermine the application target with reference to not only the degreeof similarity but also additional information on the user of eachmanagement target endpoint 10, the organization to which the userbelongs, and the like. The additional information is included in, forexample, the asset information held by the asset information server 50and the organization information held by the organization informationserver 60, and hence the application target determination unit 36 mayrefer to these pieces of information. The details of a method fordetermining the application target are also described later. Upon thedetermination of the application target in this way, the applicationtarget is reported to the configuration change instruction unit 37.Specifically, the endpoint ID of the management target endpoint 10determined as the application target is reported to the configurationchange instruction unit 37. Moreover, the configuration change ID of theconfiguration change to be applied is also transmitted from thedegree-of-similarity calculation unit 35 to the application targetdetermination unit 36, and is further transmitted to the configurationchange instruction unit 37.

As a result, the configuration change instruction unit 37 transmits aninstruction to apply the configuration change, to the configurationchange execution unit 13 of the management agent 11 operating in themanagement target endpoint 10 that has been determined as theapplication target by the application target determination unit 36 (Step323). Consequently, the configuration change execution unit 13 of themanagement agent 11 applies the configuration change to the managementtarget endpoint 10. At this time, the endpoint ID of the managementtarget endpoint 10 determined as the application target and theconfiguration change ID of the configuration change are delivered fromthe configuration change instruction unit 37 to the informationcollection unit 31.

After that, the information collection unit 31 collects a result ofapplying the configuration change to the management target endpoint 10,from the configuration change execution unit 13 of the management agent11, and stores the result in the change history DB 34 (Step 324).Specifically, the information collection unit 31 stores the endpoint ID,the configuration change ID, and a state after the configuration changeis applied, in the change history DB 34.

Upon the collection of the result of applying the configuration changein this way, the information collection unit 31 determines whether ornot the configuration change has been successfully applied to themanagement target endpoint 10 (Step 325).

As a result, if it is determined that the configuration change has beensuccessfully applied to the management target endpoint 10, thedegree-of-similarity calculation unit 35 determines whether or not anendpoint to which the configuration change has not been applied yetexists, with reference to the change history DB 34 (Step 326).

Then, if it is determined that an endpoint to which the configurationchange has not been applied yet exists, the degree-of-similaritycalculation unit 35 sets an additional reference endpoint that serves asa reference for calculating the degree of similarity (Step 327). Notethat Step 327, which is not essential, may be executed as needed. Thatis, if any of the management target endpoints 10 to which theconfiguration change has been successfully applied has a configurationthat is as different as possible from the configuration of the currentlyset reference endpoint, the degree-of-similarity calculation unit 35 mayset this management target endpoint 10 as the additional referenceendpoint. If it is determined in Step 326 that an endpoint to which theconfiguration change has not been applied yet exists or after theadditional reference endpoint is set in Step 327 as described above, theendpoint management server 30 repeats the processing of Step 321 and thesubsequent steps. That is, the degree-of-similarity calculation unit 35calculates the degree of similarity between: each of the plurality ofreference endpoints including the additional reference endpoint; andeach endpoint other than the reference endpoints, the application targetdetermination unit 36 determines an endpoint having the second highestdegree of similarity as an application target of the configurationchange, and the information collection unit 31 collects a result ofapplying the configuration change.

Meanwhile, description is given of the case where it is determined inStep 325 that the application of the configuration change to themanagement target endpoint 10 has been failed. This case means that itis determined that the application of the configuration change to any ofthe management target endpoints 10 included in the group determined inStep 322 has been failed. If such a failure is determined, first, theconfiguration change instruction unit 37 returns the management targetendpoint 10 concerning the failure to its original state before theconfiguration change is applied thereto (Step 328). Specifically, theendpoint ID of the management target endpoint 10 to which theapplication of the configuration change has been failed is deliveredfrom the information collection unit 31 to the configuration changeinstruction unit 37. Then, the configuration change instruction unit 37returns the management target endpoint 10 identified by the receivedendpoint ID to its original state.

Further in this case, subsequently, the degree-of-similarity calculationunit 35 extracts a difference between: the configuration of themanagement target endpoint 10 concerning the failure; and theconfiguration of the management target endpoint 10 to which theconfiguration change has been successfully applied immediately before(Step 329). Specifically, the endpoint ID of the management targetendpoint 10 to which the application of the configuration change hasbeen failed is delivered from the information collection unit 31 to theconfiguration change instruction unit 37. Then, the degree-of-similaritycalculation unit 35 extracts a difference between the configuration ofthe management target endpoint 10 identified by the received endpoint IDand the configuration of the management target endpoint 10 to which theconfiguration change has been successfully applied immediately before.Here, the management target endpoint 10 to which the configurationchange has been successfully applied immediately before may be definedas the management target endpoint 10 to which the configuration changehas been successfully applied immediately before, among the endpointsincluded in the group to which the configuration change has beensimultaneously applied in the latest Step 323.

As a result, the degree-of-similarity calculation unit 35 presents theextracted difference to the system administrator through the endpointmanagement console 40 (Step 330).

Moreover, if it is determined in Step 326 that an endpoint to which theconfiguration change has not been applied yet does not exist, theendpoint management server 30 ends the processing.

Note that, in the present embodiment, as long as an endpoint to whichthe configuration change has not been applied yet remains, a process ofcalculating the degree of similarity and determining an applicationtarget is performed, but the present invention is not limited thereto. Aminimum value of the degree of similarity up to which this process needsto be performed may be designated in advance, and the endpointmanagement server 30 may end the processing at the moment at which anendpoint having a degree of similarity equal to or higher than theminimum value does not remain.

Here, methods for calculating the degree of similarity by thedegree-of-similarity calculation unit 35 are described in detail.

A first method for calculating the degree of similarity is a methodincluding: calculating a correlation on the basis of the coincidence ornon-coincidence of items in each constituent element between endpointsas targets between which the degree of similarity is to be calculated;and defining the calculated correlation as the degree of similaritybetween the configurations of the endpoints. Here, examples of theconstituent elements of the endpoints include hardware, an OS,applications, applied patches, the versions thereof, and registrysetting items thereof.

FIG. 7 is a diagram for specifically describing the first method forcalculating the degree of similarity.

In the case of adopting the first calculating method, first, thedegree-of-similarity calculation unit 35 acquires, for each category,the items of the constituent elements constituting each endpoint. InFIG. 7, the degree-of-similarity calculation unit 35 acquires, for theOS, the type of the OS, the version of the OS, the presence or absenceand version of a service pack, and a language. The degree-of-similaritycalculation unit 35 also acquires: configuration change IDs foridentifying configuration changes applied to each endpoint; applicationinformation including the names and versions of applications installedin the endpoint; and device names that are the names of devices mountedon the endpoint.

Subsequently, the degree-of-similarity calculation unit 35 calculates aratio of coincident items in each constituent element, for two endpointsas targets between which the degree of similarity is to be calculated.FIG. 7 illustrates “PC001” and “PC002” as the two endpoints. Then, thenumber of coincident items in each constituent element is defined as thenumerator of the ratio. In FIG. 7, each coincident item is indicated bya check mark, and each non-coincident item is indicated by a cross mark.That is, the number of check marks in each constituent elementcorresponds to the numerator. Moreover, the denominator of the ratio isdetermined in the following manner. That is, for the OS, the number ofitems is fixed, and hence the number of items is defined as thedenominator of the ratio. Moreover, for the other constituent elements,the number of elements in the union of the listed items is defined asthe denominator of the ratio. In FIG. 7, for the OS, because the numberof check marks is “2” and the number of items is “4”, the degree ofsimilarity is expressed as “2/4”. For the configuration change ID,because the number of check marks is “3” and the number of elements inthe union of the items is “6”, the degree of similarity is expressed as“3/6”. For the application information, because the number of checkmarks is “2” and the number of elements in the union of the items is“5”, the degree of similarity is expressed as “2/5”. For the devicename, because the number of check marks is “1” and the number ofelements in the union of the items is “5”, the degree of similarity isexpressed as “1/5”.

Lastly, the degree-of-similarity calculation unit 35 calculates theaverage of the respective degrees of similarity of the constituentelements, and defines the calculated average as the degree of similaritybetween the configurations of the two endpoints. In FIG. 7, thedegree-of-similarity calculation unit 35 calculates the average of“2/4”, “3/6”, “2/5”, and “1/5”, and hence the degree of similaritybetween the configurations of the two endpoints is 0.4 (=1.6/4).

A second method for calculating the degree of similarity is a methodincluding: calculating the sum of weighted degrees of similarity, usinga table in which the degree of similarity between items or betweencombinations of items is defined for each constituent element; anddefining the calculated sum as the degree of similarity between theconfigurations of endpoints.

FIGS. 8A and 8B are diagrams for specifically describing the secondmethod for calculating the degree of similarity. In the case where thedegree of similarity between items or between combinations of items iscalculated by considering the weights of the items, a table in which thedegree of similarity between combinations of items or the degree ofsimilarity when items coincide with each other is defined for eachconstituent element is prepared in advance.

FIG. 8A is a diagram illustrating an example of an OSdegree-of-similarity table. The degree of similarity when thecombination of the items in OS 1 and the combination of the items in OS2 completely coincide with each other is defined as “1”, and the degreeof similarity indicating to what extent the combination of the items inOS 1 and the combination of the items in OS 2 coincide with each otheris defined in the table. The degree-of-similarity calculation unit 35defines the degree of similarity in a row having the same combination asthe combination of respective OSs of two endpoints as targets betweenwhich the degree of similarity is to be calculated, as the degree ofsimilarity in OS.

FIG. 8B is a diagram illustrating an example of a configuration changedegree-of-similarity table. The degree-of-similarity calculation unit 35defines the sum of the degrees of similarity for all configurationchanges commonly applied to the two endpoints as the targets betweenwhich the degree of similarity is to be calculated, as the degree ofsimilarity in configuration change. Moreover, similardegree-of-similarity tables may be prepared also for the applicationinformation and the device name, and the sum of the degrees ofsimilarity for items common between the two endpoints as the targetsbetween which the degree of similarity is to be calculated may bedefined as the degree of similarity in each of the applicationinformation and the device name.

A third method for calculating the degree of similarity is a methodincluding: defining in advance the degree of similarity between items orbetween combinations of items for each constituent element, depending onthe degree of association with a configuration change to be applied;calculating the sum of weighted degrees of similarity on the basis ofthe definition; and defining the calculated sum as the degree ofsimilarity between the configurations of endpoints.

Such tables as illustrated in FIGS. 8A and 8B are prepared for eachconfiguration change to be applied, and settings are made such that thedegrees of similarity for items concerning the configuration change tobe applied is high. This case corresponds to the third calculatingmethod.

Next, methods for determining the application target by the applicationtarget determination unit 36 are described in detail. It is assumed herethat the application target determination unit 36 determines theapplication target considering an interorganization distance in additionto the degree of similarity between the configurations of endpoints.Conceivable methods for determining the application target consideringthe interorganization distance are as follows.

A first method for determining the application target is a methodincluding preferentially applying a configuration change to endpoints inthe same organization or close organizations. In the case of adoptingthe first method for determining the application target, first, theapplication target determination unit 36 groups endpoints for eachinterorganization distance from a reference endpoint. Subsequently, theapplication target determination unit 36 selects endpoints in descendingorder of the degree of similarity to the reference endpoint, from agroup corresponding to an interorganization distance smaller than apredetermined distance, and sequentially applies the configurationchange to the selected endpoints.

A second method for determining the application target is a method foravoiding simultaneously applying a configuration change to endpoints inthe same organization or close organizations. Also in the case ofadopting the second method for determining the application target,first, the application target determination unit 36 groups endpoints foreach interorganization distance from a reference endpoint. Then, theapplication target determination unit 36 selects an endpoint having thehighest degree of similarity to the reference endpoint, from a groupcorresponding to the largest interorganization distance, and applies theconfiguration change to the selected endpoint. Subsequently, theapplication target determination unit 36 groups the endpoints for eachsum of the interorganization distance from the first reference endpointand the interorganization distance from the endpoint selectedimmediately before. Then, the application target determination unit 36selects an endpoint having the highest degree of similarity to thereference endpoint, from a group corresponding to the largest sum of theinterorganization distances, and applies the configuration change to theselected endpoint. After that, the application target determination unit36 repeats such processing as described above.

FIGS. 9A and 9B are diagrams for specifically describing a method forcalculating the interorganization distance used in the above-mentionedmethods for determining the application target. Of the two drawings,FIG. 9A illustrates an example of the asset information held by theasset information server 50. Moreover, FIG. 9B illustrates an example ofthe organization information held by the organization information server60. Note that, because an organization is expressed in a tree structurein FIG. 9B, a node corresponding to each user is referred to as a “usernode”. Moreover, a node generally referred to as an “upper node” isreferred to as a “superior node”, and a node generally referred to as a“lower node” is referred to as a “subordinate node”.

First, with reference to the asset information in FIG. 9A, theapplication target determination unit 36 obtains the user IDs of twousers who respectively use two endpoints as targets between which theinterorganization distance is to be calculated, from the endpoints ID ofthe two endpoints.

Subsequently, with reference to the organization information in FIG. 9B,the application target determination unit 36 obtains a closest commonsuperior node that is the lowest one of superior nodes common to twouser nodes respectively corresponding to the two user IDs. Note that, inthe case where one of the two user nodes is a subordinate node of theother user node, the application target determination unit 36 obtainsthe other user node as the closest common superior node.

Subsequently, with reference to the organization information in FIG. 9B,the application target determination unit 36 obtains the distance fromeach of the two user nodes to the closest common superior node. Then,the application target determination unit 36 defines the larger one ofthe two distances thus obtained, as the interorganization distance.

For example, it is discussed that, in the case where the assetinformation in FIG. 9A and the organization information in FIG. 9B areheld, the interorganization distance between the endpoint “PC001” and anendpoint “PC005” is calculated. In this case, first, with reference tothe asset information in FIG. 9A, the application target determinationunit 36 identifies a user “EMP111” from the endpoint “PC001”, andidentifies a user “EMP220” from the endpoint “PC005”. Subsequently, withreference to the organization information in FIG. 9B, the applicationtarget determination unit 36 obtains a closest common superior node“EMP000”. Subsequently, the application target determination unit 36obtains “3” as the distance from the user node “EMP111” to the closestcommon superior node “EMP000”, and obtains “2” as the distance from theuser node “EMP220” to the closest common superior node “EMP000”. Lastly,the application target determination unit 36 calculates theinterorganization distance “3” according to max (3, 2).

As described above, in the present embodiment, a configuration change issequentially applied considering the degree of similarity between theconfigurations of endpoints, and the configuration change isautomatically stopped in case of trouble. Accordingly, a trouble thatcannot be found at the time of advance testing can be prevented fromsimultaneously occurring in a large indefinite number of endpoints, andinfluences such as suspension of business can be minimized.

Moreover, in the present embodiment, a configuration change issequentially applied to endpoints in descending order of the degree ofsimilarity in configuration to a reference endpoint. Accordingly, evenif a trouble occurs in a given endpoint, a difference between theconfiguration of the given endpoint and the configuration of an endpointto which the configuration change has been successfully applied issmall, and hence problem determination work is facilitated.

Hardware Configuration of Endpoint Management Server according toPresent Embodiment

FIG. 10 is a diagram illustrating a hardware configuration example ofthe endpoint management server 30 according to the present embodiment.As illustrated in FIG. 10, the endpoint management server 30 includes: acentral processing unit (CPU) 30 a as arithmetic means; a main memory 30c that is connected to the CPU 30 a through a motherboard (M/B) chip set30 b; and a display mechanism 30 d that is similarly connected to theCPU 30 a through the M/B chip set 30 b. Moreover, a network interface 30f, a magnetic disk device (HDD) 30 g, an audio mechanism 30 h, akeyboard/mouse 30 i, and an optical drive 30 j are connected to the M/Bchip set 30 b through a bridge circuit 30 e.

Note that the constituent elements in FIG. 10 are connected to oneanother through buses. For example, the CPU 30 a and the M/B chip set 30b are connected to each other through a CPU bus, and the M/B chip set 30b and the main memory 30 c are connected to each other through a CPUbus. Moreover, although the M/B chip set 30 b and the display mechanism30 d may be connected to each other through Accelerated Graphics Port(AGP), in the case where the display mechanism 30 d includes a videocard compliant with PCI Express, the M/B chip set 30 b and the videocard are connected to each other through a PCI Express (PCIe) bus.Moreover, for example, PCI Express can be used to connect the networkinterface 30 f to the bridge circuit 30 e. Moreover, for example, SerialAT Attachment (ATA), parallel transfer ATA, and Peripheral ComponentsInterconnect (PCI) can be used to connect the magnetic disk device 30 gto the bridge circuit 30 e. Further, Universal Serial Bus (USB) can beused to connect each of the keyboard/mouse 30 i and the optical drive 30j to the bridge circuit 30 e.

Here, the present invention may be achieved entirely by hardware, andmay be achieved entirely by software. The present invention may also beachieved by both hardware and software. Moreover, the present inventioncan be achieved as a computer, a data processing system, and a computerprogram. The computer program can be provided in the state where thecomputer program is stored in a computer-readable medium. Conceivablemedia include electronic, magnetic, optical, electromagnetic, infrared,and semiconductor systems (apparatuses, devices) as well as apropagation medium. Moreover, examples of the computer-readable mediuminclude a semiconductor, a solid-state memory, a magnetic tape, aremovable computer diskette, a random access memory (RAM), a read onlymemory (ROM), a rigid magnetic disk, and an optical disk. Examples ofthe optical disk at present include a compact disc read only memory(CD-ROM), a compact disc read/write (CD-R/W), and a DVD.

Hereinabove, the present invention has been described by way of theembodiment, and the technical range of the present invention is notlimited to the above-mentioned embodiment. It is obvious for thoseskilled in the art that various changes and alternative modes of thepresent invention can be adopted without departing from the spirit andrange of the present invention.

REFERENCE SIGNS LIST

10 . . . management target endpoint

20 . . . test environment endpoint

30 . . . endpoint management server

31 . . . information collection unit

32 . . . configuration information DB

33 . . . working status DB

34 . . . change history DB

35 . . . degree-of-similarity calculation unit

36 . . . application target determination unit

37 . . . configuration change instruction unit

40 . . . endpoint management console

50 . . . asset information server

60 . . . organization information server

What is claimed is:
 1. A method for updating software or for changingconfiguration of software installed in a plurality of terminals,comprising: giving an instruction to update the software or to changethe configuration of the software installed in a first terminal of theplurality of terminals; recognizing that the software installed in thefirst terminal has been successfully updated or the configuration of thesoftware installed in the first terminal has been successfully changed;selecting, in response to the recognition that the software installed inthe first terminal has been successfully updated or the configuration ofthe software installed in the first terminal has been successfullychanged, a second terminal of the plurality of terminals in a case wherea degree of similarity between a configuration of the first terminal anda configuration of the second terminal is equal to or higher than apredetermined reference value; and giving an instruction to update thesoftware or to change the configuration of the software installed in thesecond terminal.
 2. The method of claim 1, wherein the second terminalis selected in a case where a degree of priority of a user of the secondterminal is equal to or higher than a predetermined reference value. 3.The method of claim 1, further comprising: selecting, in response to therecognition that the software installed in the first terminal has beensuccessfully updated or the configuration of the software installed inthe first terminal has been successfully changed, a third terminal ofthe plurality of terminals in a case where a degree of similaritybetween the configuration of the first terminal and a configuration ofthe third terminal is equal to or higher than a predetermined referencevalue; and giving an instruction to update the software or to change theconfiguration of the software installed in the third terminal.
 4. Themethod of claim 3, wherein the second terminal and the third terminalare selected in a case where a degree of association between aninstallation place of the second terminal and an installation place ofthe third terminal satisfies a predetermined condition.
 5. The method ofclaim 3, wherein the second terminal and the third terminal are selectedin a case where a degree of association between an installation place ofthe second terminal and an installation place of the third terminalsatisfies a predetermined condition.
 6. The method of claim 1, furthercomprising: recognizing that the software installed in a third terminalof the plurality of terminals has been successfully updated or theconfiguration of the software installed in a third terminal of theplurality of terminals has been successfully changed; selecting, inresponse to the recognition that the software installed in the thirdterminal has been successfully updated or the configuration of thesoftware installed in the third terminal has been successfully changed,a fourth terminal of the plurality of terminals in a case where at leastany one of: a degree of similarity between the configuration of thefirst terminal and a configuration of the fourth terminal, and a degreeof similarity between a configuration of the third terminal and theconfiguration of the fourth terminal is equal to or higher than apredetermined reference value; and giving an instruction to update thesoftware or to change the configuration of the software installed in thefourth terminal.
 7. The method of claim 1, further comprising:generating information indicating a difference between a configurationof a third terminal of the plurality of terminals and a configuration ofa fourth terminal of the plurality of terminals, in a case where it isnot recognized that the software installed in the fourth terminal hasbeen successfully updated or the configuration of the software installedin the fourth terminal has been successfully changed after it isrecognized that the software installed in the third terminal has beensuccessfully updated or the configuration of the software installed inthe third terminal has been successfully changed.